System for handling meta data for describing one or more resources and a method of handling meta data for describing one or more resources

ABSTRACT

A system for handling meta data for describing one or more resources, wherein the one or more resources are deliverable to a common group of users at one or more user terminals, the system including: a resource server for storing the one or more resources for delivery to at least one of the common group of users at one or more user terminals, an administration server arranged to serve the common group of users at the one or more user terminals, for storing a set of meta data for describing the learning resources, the meta data having a format including a non-semantic tag which is customisable in accordance with the common group of users&#39; requirements.

FIELD OF THE INVENTION

The invention relates to a system for handling meta data for describingone or more resources and a method of handling meta data for describingone or more resources.

BACKGROUND INFORMATION

Systems and methods of handling meta data for describing one or moreresources are known in the art. Such systems and methods may findapplication in e-learning systems and methods. They are however, notlimited in this respect, and have further application in other fields,for example, data base management and other fields where meta data isused.

Systems and applications for providing e-learning, also referred to inthe art, inter alia, as computer based training, computer assistedinstruction and technology supported learning, are known. Suchapplications and systems use content, for example, lectures and bookchapters, which are delivered to users electronically. In order todescribe the e-learning content, meta data is associated with thecontent. XML (extensible mark-up language) based standards is onetechnology, which is conventionally used to define meta data. During thecreation of e-learning content it is desirable to keep track of the metadata associated with the content. To this end, several standards fordefining e-learning meta data have evolved. For example, learning objectmeta data standard (LOM) and Dublin Core. However, in order toaccommodate the needs of a broad range of users of the e-learningcontent including e-learning participants as well as e-learningproviders, a “one size fits all” approach is used. As a result, theexisting standards include large quantities of meta data definitionswhich are not required by some users or not available to other users.Thus, a large proportion of conventional meta data is optional. Thisresults in a particular user or group of users, for example, anorganization, who wish to use the standards, not being able to rely on aparticular meta data, which they require, being present in aconventional meta data file. For example, conventional standards, suchas LOM and Dublin Core have a relatively large set of fixed values witha predefined semantic which can be used in documents formatted accordingto these standards using for example, an XML tag. For example, fixedvalues with a predefined semantic include author, title, etc. Due totheir fixed values, defined semantic and predefined XML tags, suchstandards are useful for exchanging meta data between differentindependent users (for example, users not connected by the sameintranet) or different organisations. However, as mentioned above, it isnot optimal for use within an organisation. Due to the large number ofpossible values necessary in order to account for most possible userrequirements, most values are optional and can contain arbitrary text.Further, there is no restriction with respect to which meta data valuesare to be maintained and which format they should preferably be in for aparticular user or organisation. Yet further, it is not possible tomaintain meta data, that may not be covered by the possible fixed valuesof the standards, for example, meta data that may be unique to aparticular user or organisation.

SUMMARY OF THE INVENTION

It is an object of the present invention to address those problemsencountered with conventional systems. For example, it is an object ofthe present invention to improve the delivery of resources to users. Itis a further object to address those problems encountered withconventional meta data standard technology, such as XML. For example, itis desirable to improve the maintenance of meta data within a group ofcommon users, an organization or the like.

According to a first aspect of the invention, there is provided a systemfor handling meta data for describing one or more resources, wherein theone or more resources are deliverable to a common group of users at oneor more user terminals, the system including: a resource server forstoring the one or more resources for delivery to at least one of thecommon group of users at one or more user terminals, an administrationserver arranged to serve the common group of users at the one or moreuser terminals, for storing a set of meta data for describing thelearning resources, the meta data having a format including anon-semantic tag which is customisable in accordance with the commongroup of users' requirements.

According to a second aspect of the invention, there is provided amethod of handling meta data for describing one or more resources, themethod comprising delivering one or more learning resources to a commongroup of users at one or more user terminals, the method furtherincluding: storing in a resource server the one or more resources fordelivery to at least one of the common group of users at one or moreuser terminals, storing a set of meta data for describing the resourcesin an administration server arranged to serve the common group of usersat the one or more user terminals, the meta data having a formatincluding a non-semantic tag which is customisable in accordance withthe common group of users' requirements.

According to a third aspect of the invention, there is provided a userterminal.

According to a fourth aspect of the invention, there is provided aprogram storage device readable by a processing apparatus, the deviceembodying a program of instructions executable by the processor.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an architecture incorporating an embodiment of the presentinvention.

FIG. 2 is a listing of a code for implementing an embodiment of thepresent invention.

FIG. 3 shows a customizing user interface of a learning solutionaccording to an embodiment of the invention.

FIG. 4 shows an learning solution authoring environment which can beused to maintain the meta data values according to an embodiment of theinvention.

DETAILED DESCRIPTION

FIG. 1 shows an architecture incorporating an embodiment of the presentinvention. The architecture includes a system 2, 4 for handling metadata for describing one or more resources. Further, the system isarranged to deliver one or more resources 6 to common group of users 8.In one embodiment, the system is an e-learning system and the one ormore resources include one or more learning resources. The system mayinclude a learning resource system, also referred to as a content serveror learning resource server 2, for storing the one or more learningresources for delivery to at least one of the common group of users atone or more user terminals 8. Systems and methods of handling meta datafor describing one or more resources are known in the art. Such systemsand methods may find application in e-learning systems and methods. Theyare however, not limited in this respect, and have further applicationin other fields, for example, data base management and other fieldswhere meta data is used. The one or more user terminal 8 typicallycomprises a processor and a storage device 8 a, for example, a harddrive. To interact with a user, the user terminal may comprise akeyboard and pointing device 8 b, or the like and a display, forexample, a monitor including a screen. The user terminal may be adesktop unit. Alternatively, it may be a handheld device, or the like,such as a laptop computer, etc. Data may be exchanged between theprocessor and the storage device in the hard drive. It may also beexchanged between the keyboard and the display and between the displayand the hard drive. In FIG. 1 arrows linking entities indicates thatdata may be exchanged between such linked entities.

The system further includes an administration system 4 arranged to servethe common group of users at the one or more user terminals, for storinga set of meta data for describing the learning resources, the meta datahaving a format including a non-semantic tag which is customisable inaccordance with the common group of users. The users are connected tothe administration system 4 and the learning resource system 2 bycommunication links over which data may be communicated. In theembodiment shown, the learning resource system 2 is connected to theuser terminals 8 and the administration system 4 via the internet 12, orthe like. In an alternative embodiment, the learning resource system 2and the administration system 4 are provided on the same communicationsnetwork. For example, on a network provided within one organisation,such as an intranet, LAN (local area network), or the like.

A group of common users may be a group of users having substantiallysimilar requirements in terms of the meta data they desire to describethe learning resource or resources they are interested in. The group ofcommon users may be based in an organisation, or may be distributedamongst a variety of different organisations. Organisations include, butare not limited to, enterprises including companies and the like,non-profit organisations, such as charities, universities, schools andother learning establishments. The group of common users may be servedby the same server. Alternatively, they may be served by differentservers. The administration system may be implemented using a server 4,such as, for example, the SAP R/3 4.6C and learning solution (LSO)Add-on, which may also be referred to as the LSO backend. Theadministration system 4 may include a database of learner accounts andcourse information. In particular, it may be a platform as part of theLSO to enable the administration of e-learning, for example, thebusiness of delivering and creating content. For example, the databasemay include the learner account, may include demographic data about thelearner, for example, a name, an age, a sex, an address, a company, aschool, an account number and a bill. It may further include his/herprogress through the course material. For example, places visited, testscompleted, skills gained, knowledge acquired and competency using thematerial. The administration system 4 may also provide additionalinformation about courses, such as the courses offered, theauthor/instructor of a course and the most popular courses. Further, inan embodiment of the invention, since the meta data format itself doesnot contain any semantic information, the semantic organization, orcommon group of users, wide information about the meta data values isstored in a central dictionary, for example, in the administrationsystem 4. However, in an alternative embodiment, the dictionary storingthe semantic information may be stored in another database accessible tothe group of users or organization, for example, in the learningresource system 2.

The content management system 2 may include a learning content server 2.The learning content server 2 may be implemented using an WebDAV server.The learning content server 2 may include a content repository 16. Thecontent repository 16 may store course files 6 and media files 6 thatare used to present a course to a learner at the learning station 8. Thecourse files 6 may include the structural elements that make up a courseand may be stored as XML files The media files may be used to store thecontent that is included in the course and assembled for presentation tothe learner at the learning station.

The learning management system may include a content player. The contentplayer may be implemented using a server, such as, an SAP J2EE Engine.The content player is used to obtain course material from the contentrepository 16.

The learning management system may also include an interface forexchanging information with the administration system. For example, thecontent player may update the learner account information as the learnerprogresses through the course material.

FIG. 2 is a listing of a code for implementing an embodiment of thepresent invention. Each line of the code shown in FIG. 2 is repeatedhereinbelow together with an explanation of the meaning of eachparticular line.

Description of the code shown in FIG. 2:

“<?xml version=“ 1.0” encoding=“UTF-8”?>”

-   -   A generic XML header defining the XML version and character        encoding for this XML document.

“<!DOCTYPE LSOMETADATA”

-   -   Start of a DTD (Document Type Definition) for this XML        document—the DTD describes a valid syntax for the document and        allows easy validation of the document.    -   This line simply defines that the root tag for this document is        LSOMETADATA.

“[<!ELEMENT LSOMETADATA (VALUE)*>”

-   -   This line defines that the LSOMETADATA tag can contain only        VALUE tag and the * defines that there can be 0 or more of these        VALUE tags.

“<!ATTLIST LSOMETADATA VERSION NMTOKEN #REQUIRED>”

-   -   The line defines that the LSOMETADATA tag has a mandatory        (#REQUIRED) numerical (NMTOKEN) attribute VERSION.

“<!ELEMENT VALUE (#PCDATA)>”

-   -   The line defines that the VALUE tag can contain any kind of        data.

“<!ATTLIST VALUE”

-   -   The line defines that the attributes for the tag VALUE follow.        -   “TYPE CDATA #REQUIRED”    -   The line defines the mandatory attribute TYPE of tag VALUE.        -   “NAME CDATA #REQUIRED>]>”    -   The line defines the mandatory attribute NAME of tag VALUE and        the end of the DTD (]>).

The lines given above are common to XML documents of this type andcontain no metadata, these lines only define how a typical valid metadata file may look like.

The following lines contain the actual meta data, in particular, themeta data according to an embodiment of the invention:

“<LSOMETADATA VERSION=“1”>”

-   -   This tag starts the LSOMETADATA document with the attribute        VERSION set to 1.

“<VALUE TYPE=“xs:string” NAME=“author”>author</VALUE>”

-   -   This tag defines the metadata value “author” (between the        <VALUE> and </VALUE> tags) and the attributes TYPE (“xs:string”)        and NAME (“author”).

“<VALUE TYPE=“xs:string” NAME=“title”>title</VALUE>”

-   -   This tag defines the metadata value “title” with the attributes        TYPE (“xs:string”) and NAME (“title”).

“</LSOMETADATA>”

-   -   This tag defines the end of the metadata document.

To address the problems identified in the prior art, a meta data formataccording to a predefined standard, such as XML, is introduced. The metadata describes data, typically, the learning resource 6. The XML basedmeta data format is free of semantics. In particular, the semanticmeaning is dissociated from the tag 20. Instead of using tags withsemantic, as is the conventional approach, generic tags 20 are usedwhich can be used to store key value pairs, for example, the value andthe value type. The code shown in FIG. 2 is a sample of such a genericmeta data file which contains the meta data values author 21 and title22, which are both of type string. For the code appearing in FIG. 2, thestandard XML notation applies. For example, it is commented that it isconventional in XML notation to depict meta data in capitals. In FIG. 2,the words author and title are lower case, indicating that theyrepresent real information, rather than semantic information. The metadata file includes meta data 23, in particular, learning solution metadata. According to an embodiment of the invention, the content server 2stores the meta data 23 together with the learning resource 6. Inparticular, the meta data format including the generic tag 20 is storedtogether with a semantic look-up table, also referred to as adictionary. In an alternative embodiment, the learning resource 6 isstored remotely from the standard format meta data. The generic metadata 23 is stored on the administration server 4. When a learningresource 6 is imported, the standard meta data is transformed into thegeneric format. Further, when a learning resource 6 is exported to aremote administration server 4, the metadata is transformed out of thegeneric format 23. In one embodiment, the metadata and transformationsare stored on the learning solution back end LSO.

Since there is no common standard for e-learning meta data and no fixedset of data relevant for all users, the inventors have found a differentapproach. According to an embodiment of the invention, instead of usinga format with fixed data, a format without fixed data, such as, forexample, author, title, etc. In contrast to conventional meta data, themeta data according to an embodiment of the invention, includes a uniqueidentifier, also referred to as a key, importance classification, forexample, if the value is mandatory or optional, a type and a value foreach data. The key is a unique identifier representing the semantic ofthe value, for example, the author. However, the set of possible keys isnot defined a priori, but is customizable by the user in the LSOe-learning system. Together with the key, the user may customize theimportance of the data, for example, whether it is mandatory oroptional, and the data type, for example, whether it is an integer,string, date, etc. The data format according to an embodiment of theinvention allows the customer to keep track of which meta data fields hewants and by marking a data as mandatory is able to ensure that the datais maintained in the e-learning system 2, 4.

In one embodiment, the administration server 4 includes a meta dataprocessor 14, wherein the generic format 23 further includes a uniqueidentifier 20 for identifying the non-semantic tag 20 to the meta dataprocessor 14. In a further embodiment, the learning resources 6 storedon the learning resource server 2 are described by one or more meta data23 having a format 20 in accordance with a predefined standard. In afurther embodiment, the meta data processor 14 is arranged to transformthe meta data having the format in accordance with the predefinedstandard in to the format 23 including a non-semantic tag 20 using theunique identifier. In particular, the meta data processor 14 is arrangedto at least one of import and export meta data in a format bytransforming the format into or from another meta data format in apredefined standard.

FIG. 3 shows a customizing user interface of a learning solutionaccording to an embodiment of the invention. In particular, the userinterface 30 of the learning solution can be used to customize the metadata values 23 which are to be maintained for e-learning courses usedwithin the learning solution system 2, 4. The customizing is carried outin the central customizing of the learning solution backend LSO, whichis part of the e-learning system 2, 4. In one embodiment, the e-learningsystem 2, 4 further comprising a user interface generator 16 forgenerating a user interface 30 which a user can interact with tocustomize the meta data 23 in accordance with the user's or the commongroup of users' requirements. In a further embodiment, the userinterface 30 includes a screen displaying one or more fields 31-34wherein at least one of a meta data identification 31, a mandatoryindication 32, a data type 33 and a metadata description 34 may beentered, respectively. The meta data identification 31 indicates thetype of meta data, for example, author, description, editor, expiringdate, keywords, language, last edited, learning objectives, learningtime, name, owner, provider, publisher, reason, release, release date,skills, status, subject, etc. . . .

During the customizing, according to an embodiment of the presentinvention, the following information is maintained: The meta dataidentification 31. The meta data identification 31 is a uniqueidentification and corresponds to the name used in the XML format todescribe the value. The required indication 32: the required indication32 indicates whether the value is mandatory (required) or optional. Thedata type field 33 indicates the type of meta data to describe the metadata, for example, whether the meta data for a particular type is astring, a date, boolean, integer, . . . etc.

The meta data description field 34 is a language dependent descriptionof the value for use in the user interface. In particular, the meta datadescription describes the meta data identified in metadataidentification field 31.

The mandatory indication 32 allows the user to customize whether thedata type, for example, those data types listed above, such as author,title, etc. are required or not for a particular user of group of users,in particular for a particular common group of users. In the embodimentshown in FIG. 3, it is seen that the meta data types author, language,last edited, leaning time and name have been customized as beingrequired for the common group of users in question. In some instances,the meta data description 34 is the same as the meta data identification31, for example, for the meta data type author. However, for otherinstances, it may be desirable to customize the meta data descriptionfor the user or, in particular, for the common group of users. In whichcase, the meta data description 34 may be customized so that it isdifferent from the meta data identification 31, for example, LastChanged On, Learning Duration, etc. . . . In this way, the meta datadescription can be presented to the common group of users in terms whichare familiar.

Having customised the meta data in accordance with the requirements of aparticular group of users, the customized settings can be saved byclicking save icon 35.

Other functions which may be provided according to further embodimentsof the invention include: adding new meta data. This may be done bypressing the “sNew Entries” icon 36 which displays a user interface forcreating new entries. Further, an entry or entries may be deleted. Thismay be done by pressing a “Delete Entries” icon 37 which displays a userinterface for deleting an entry or entries. A further function includeschanging the description of the meta data and translating it. In oneembodiment, the description of the meta data is maintained in the logonlanguage. In this embodiment, to translate a description into anotherlanguage, for example, German, would require the user to log on inGerman. However, in an alternative embodiment, the description of themeta data is translatable once a user is already logged on. In this way,the flexibility of the system with respect to a user's preferences isimproved.

An application using the meta data, for example, as shown in FIG. 4,first accesses a central dictionary 18 to retrieve the known values andthen present a corresponding user interface using the actual data from ameta data file. The location of the stored central dictionary 18, shownin FIG. 1, is not limited. In the embodiment shown in FIG. 1 it islocated on the administration server 4. However, in an alternativeembodiment, it may be located on the learning server 2 or a furtherserver or storage medium.

FIG. 4 shows an learning solution authoring environment which can beused to maintain the meta data values according to an embodiment of theinvention. In particular, FIG. 4 shows an example of a screen shot ofthe learning solution authoring environment where the meta data for ane-learning course can be maintained. The information about the meta datafields, their data type and whether they are mandatory or optional isretrieved from the learning solution customizing stored, for example, onthe R/3 LSO backend. The meta data values are read from the e-learningcourses XML meta data file. In particular, FIG. 4 shows a user interfaceincluding a screen 40 wherein which the user can edit meta data. Thescreen displays at least one of mandatory tab strip 42, optional tabstrip 43 and additional tab strip 44.

The tab strips 42, 43, 44 show where the fields are grouped according totheir mandatory indication. For example, the Mandatory fields tab 42contains all metadata customized as mandatory. The Optional tab 43contains all metadata customized as not mandatory. The Additional tab 44contains all metadata values encountered, that are not defined in thecustomizing. For example, this may occur if the customizing is changedor metadata from foreign systems is imported.

In each of the three tabs 42, 43, 44 each row 47-51 represents ametadata as customized. The Field column 52 contains the languagedependent description as entered in the customizing, except for theadditional fields where the content of the NAME attribute from themetadata file is used, since there is no customizing for this metadata.

The value column 53 contains the value as stored in the metadata file ifit is available, otherwise no value is displayed. The value cells thatdo not allow input are metadata the authoring environment automaticallymaintains which the user therefore the user cannot change.

The third row on each tab is a single icon which would switch the row tomulti line editing in order to enter a value that does not fit into asingle line.

The user is able to edit the fields 47, 48, 49, 50, 51, also referred toas data types, in order to maintain the meta data. In particular, theuser is able to maintain the field (i.e. the data type, also referred toas the meta data description with reference to FIG. 3). In a furtherembodiment, the screen includes at least one of an confirm icon 45 whoseselection by a users saves the edited meta data and a cancel icon 46whose selection by a user cancels the edited meta data.

The invention as described can be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombination thereof. An apparatus according to the present invention canbe implemented in a computer program product tangibly embodied in amachine readable storage device for execution by a programmableprocessor; and method steps of the invention can be performed by aprogrammable processor executing a program of instructions to performfunctions of the invention by operating on input data and generatingoutput. The invention can be implemented in one or more computerprograms that are executable on a programmable system including at leastone programmable processor coupled to receive data and instructionsfrom, and to transmit data and instructions to, a data storage system,at least one input device, and at least one output device. Each computerprogram can be implemented in a high-level procedural or object-orientedprogramming language, or in assembly or machine language if desired; andin any case, the language can be a compiled or interpreted language.Suitable processors include, by way of example, both general and specialpurpose microprocessors. Typically, a processor will receiveinstructions and data from a read-only memory and/or a random accessmemory. Typically, a computer will include one or more mass storagedevices for storing data files; such devices include magnetic disks,such as internal hard disks and removable disks; magneto-optical disks;and optical disks. Storage devices suitable for tangibly embodyingcomputer program instructions and data include all forms of non-volatilememory, including by way of example, semiconductor memory devices, suchas EEPROM, and flash memory devices; magnetic disks such as internalhard disks and removable disks; magneto-optical disks; and CD-ROM disks.Any of the foregoing can be supplemented by, or incorporated in ASICs(application specific integrated circuits).

To provide for interaction with a user, the invention can be implementedon a computer system having a display device such as a monitor or LCDscreen for displaying information to the user and a keyboard and apointing device such as a mouse or a trackball by which the user canprovide input to the computer system. The computer system can beprogrammed to provide a graphical user interface through which computerprograms interact with users.

Whilst specific embodiments of the invention have been described above,it will be appreciated that the invention may be practiced otherwisethan as described. The description is not intended to limit theinvention.

1. A system for handling meta data for describing one or more resources,wherein the one or more resources are deliverable to a common group ofusers at one or more user terminals, the system including: a resourceserver for storing the one or more resources for delivery to at leastone of the common group of users at one or more user terminals; and anadministration server arranged to serve the common group of users at theone or more user terminals and for storing a set of meta data fordescribing the learning resources, the meta data being stored in aformat, the format being operative as follows: including a commentwithin an XML document, the comment defining: a root tag associated withthe document, the root tag having a numerical attribute representing theversion of the root tag; an identification of an additional tagcontained within the root tag, where the only tag contained within theroot tag is the identified additional tag; a type attribute associatedwith the identified additional tag, the type attribute requiring a typeof data contained within the identified additional tag; a name attributeassociated with the identified additional tag, the name attributerequiring a name of the data contained within the identified additionaltag; responsive to importing a learning resource related to the roottag, receiving meta data associated with the learning resourcecontaining a plurality of tags; comparing the tag names of the receivedmeta data to a list of name attributes associated with the identifiedadditional tag contained within the root tag to identify supported metadata; extracting the meta data tag name and value pairs from theidentified supported meta data, ignoring the remaining unsupported metadata; creating a meta data document containing the root tag, the versionof the meta data document, and the identified additional tag, theidentified additional tag containing the extracted meta data tag name asthe name attribute, and the value pair associated with the meta data tagname, the value pair being contained in the meta data document in theformat specified by the type attribute; responsive to a requestcontaining the root tag to later export the learning resource,retrieving the created meta data document containing the root tag;extracting the meta data tag name from the name attribute and the metadata value associated with the meta data tag name from the root tag; andupdating the meta data tag in the learning resource with any extractedchanges to the meta data value associated with the meta data tag name.2. The system according to claim 1, wherein the administration serverincludes a meta data processor, and wherein the format further includesa unique identifier for identifying the generic tag to the meta dataprocessor.
 3. The system according to claim 1, wherein the resourcesstored on the resource server are described by one or more meta datahaving a format in accordance with a predefined standard.
 4. The systemaccording to claim 3, wherein the meta data processor is arranged totransform the meta data having the format in accordance with thepredefined standard in to the format including the generic tag using theunique identifier.
 5. The system according to claim 1, wherein the metadata processor is arranged to at least one of import and export metadata in a format by transforming the format into or from another metadata format in a predefined standard.
 6. The system according to claim3, wherein the meta data is stored together with the resource.
 7. Thesystem according to claim 3, wherein the predefined standard is XML. 8.The system according to claim 1, further comprising a user interfacegenerator for generating a user interface which a user can interact withto customize the meta data in accordance with the user's or the commongroup of users' requirements.
 9. The system according to claim 8,wherein the user interface includes a screen displaying one or morefields wherein at least one of a meta data identification, a mandatoryindication, a data type and a metadata description may be entered,respectively.
 10. The system according to claim 8, wherein the userinterface includes a screen wherein which the user can edit meta data.11. The system according to claim 10, wherein the screen displays atleast one of mandatory fields, optional fields and additional fields.12. The system according to claim 11, wherein the screen includes atleast one icon selected from the group consisting of a confirmation iconthat results in saving the edited meta data when selected by the userand a cancel icon that results in canceling the edited meta data whenselected by the user.
 13. The system according to claim 1, wherein thesystem is an e-learning system and the one or more resources comprises alearning resource.
 14. The system according to claim 13, wherein theresource server is a learning resource server for storing the one ormore learning resources.
 15. A program storage device readable by aprocessing apparatus, the device embodying a program of instructionsexecutable by the processor to perform the steps of: delivering one ormore learning resources to a common group of users at one or more userterminals; storing in a resource server the one or more resources fordelivery to at least one of the common group of users at one or moreuser terminals; and storing a set of meta data for describing theresources in an administration server arranged to serve the common groupof users at the one or more user terminals, the meta data being storedin a format, the format being operative as follows: including a commentwithin an XML document, the comment defining: a root tag associated withthe document, the root tag having a numerical attribute representing theversion of the root tag; an identification of an additional tagcontained within the root tag, where the only tag contained within theroot tag is the identified additional tag; a type attribute associatedwith the identified additional tag, the type attribute requiring a typeof data contained within the identified additional tag; a name attributeassociated with the identified additional tag, the name attributerequiring a name of the data contained within the identified additionaltag; responsive to importing a learning resource related to the roottag, receiving meta data associated with the learning resourcecontaining a plurality of tags; comparing the tag names of the receivedmeta data to a list of name attributes associated with the identifiedadditional tag contained within the root tag to identify supported metadata; extracting the meta data tag name and value pairs from theidentified supported meta data, ignoring the remaining unsupported metadata; creating a meta data document containing the root tag, the versionof the meta data document, and the identified additional tag, theidentified additional tag containing the extracted meta data tag name asthe name attribute, and the value pair associated with the meta data tagname, the value pair being contained in the meta data document in theformat specified by the type attribute; responsive to a requestcontaining the root tag to later export the learning resource,retrieving the created meta data document containing the root tag;extracting the meta data tag name from the name attribute and the metadata value associated with the meta data tag name from the root tag; andupdating the meta data tag in the learning resource with any extractedchanges to the meta data value associated with the meta data tag name.